Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

How the DCU differs from a Progress Dynamics session

In essence, the DCU is a minimal Progress Dynamics session running without most of the normal framework managers (such as Session, General, Profile, and Referential Integrity). The startup procedure starts only the Configuration File Manager and the Connection Manager. The startup procedure then runs the Configuration File Manager’s initializeSession procedure. This means that the DCU has access to the Configuration File Manager APIs, such as getManagerHandle, getSessionParam, and setSessionParam. The DCU can also use the Configuration File Manager’s XML parsing facility to establish the initial environment.

Beyond the Configuration File and Connection Managers, the DCU also loads two special managers that contain the DCU’s API, the Installation User Interface, and ICFDB Install Managers. You can add other custom managers and APIs to what the DCU loads. You can then access them for your own upgrade processes.

Because the DCU uses the Configuration File Manager, parameters supported by the Configuration File Manager on the command line are also supported for the DCU. You can, for example, override the standard configuration file by specifying the ICFCONFIG parameter.